Authentication using physical interaction characteristics

ABSTRACT

User physical interaction characteristics information or the way a user physically interacts with a device is analyzed to aid in authenticating a user of a device. User physical interaction characteristics information such as swipe speed, finger area, finger conductivity, finger angle, device angle, movement patterns, acceleration, etc., provide signatures that are distinctive for particular individuals and possibly unique if measured to a sufficiently high level of precision. In some examples, a device measures finger positions, finger pad sizes, moisture level, acceleration, displacement, and changes in finger pad size for a particular user and compares the measurements to physical interaction characteristics measured during subsequent usage of the device to verify that a user is an authorized user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims benefit under 35 U.S.C.§120 to U.S. application Ser. No. 13/415,930, filed Mar. 9, 2012 andtitled “AUTHENTICATION USING PHYSICAL INTERACTION CHARACTERISTICS”,issued as U.S. Pat. No. 9,256,715 on Feb. 9, 2016, the entirety of whichis incorporated herein by reference for all purposes.

TECHNICAL FIELD

The present disclosure relates to authentication using physicalinteraction characteristics.

DESCRIPTION OF RELATED ART

Many devices such as mobile devices require entry of a passcode such asa password, code sequence, or pin before a user can access the mobiledevice. The passcodes may be application level, platform/operatingsystem level, or hardware read only memory (ROM) level. In someinstances, devices may have a biometric scanner such as a fingerprintreader that will scan a fingerprint in addition to requiring a passcode.Some devices may use a camera to perform facial recognition prior toallowing user access. Still other systems require a password along withcorrect responses to a particular set of challenge questions.

Although passcode based authentication and available biometric basedauthentication systems are effective, they have limitations. Forexample, some biometric based authentication systems are not fullyaccurate and lead to many false positives and negatives. Passcodessimilarly have limitations. Consequently, the techniques of the presentinvention provide improved mechanisms for authentication.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure may best be understood by reference to the followingdescription taken in conjunction with the accompanying drawings, whichillustrate particular embodiments of the present invention.

FIG. 1 illustrates a particular system implementing multilevel passcodeauthentication.

FIG. 2 illustrates a particular example of multilevel passcodeauthentication.

FIG. 3 illustrates a particular example multilevel passcodeauthentication using a user identity confidence score.

FIG. 4 illustrates a particular example of technique for user physicalinteraction characteristics identification.

FIG. 5 illustrates a particular example of a computer system.

DESCRIPTION OF PARTICULAR EMBODIMENTS

Reference will now be made in detail to sonic specific examples of theinvention including the best modes contemplated by the inventors forcarrying out the invention. Examples of these specific embodiments areillustrated in the accompanying drawings. While the invention isdescribed in conjunction with these specific embodiments, it will beunderstood that it is not intended to limit the invention to thedescribed embodiments. On the contrary, it is intended to coveralternatives, modifications, and equivalents as may be included withinthe spirit and scope of the invention as defined by the appended claims.

For example, the techniques and mechanisms of the present invention willbe described in the context of particular platforms and operatingsystems. However, it should be noted that the techniques and mechanismsof the present invention apply to a variety of different platforms andoperating systems. In the following description, numerous specificdetails are set forth in order to provide a thorough understanding ofthe present invention. Particular example embodiments of the presentinvention may be implemented without some or all of these specificdetails. In other instances, well known process operations have not beendescribed in detail in order not to unnecessarily obscure the presentinvention.

Various techniques and mechanisms of the present invention willsometimes be described in singular form for clarity. However, it shouldbe noted that some embodiments include multiple iterations of atechnique or multiple instantiations of a mechanism unless notedotherwise. For example, a system uses a processor in a variety ofcontexts. However, it will be appreciated that a system can use multipleprocessors while remaining within the scope of the present inventionunless otherwise noted. Furthermore, the techniques and mechanisms ofthe present invention will sometimes describe a connection between twoentities. It should be noted that a connection between two entities doesnot necessarily mean a direct, unimpeded connection, as a variety ofother entities may reside between the two entities. For example, aprocessor may be connected to memory, but it will be appreciated that avariety of bridges and controllers may reside between the processor andmemory. Consequently, a connection does not necessarily mean a direct,unimpeded connection unless otherwise noted.

Overview

User physical interaction characteristics information or the way a userphysically interacts with a device is analyzed to aid in authenticatinga user of a device. User physical interaction characteristicsinformation such as swipe speed, finger area, finger conductivity,finger angle, device angle, movement patterns, acceleration, etc.,provide signatures that are distinctive for particular individuals andpossibly unique if measured to a sufficiently high level of precision.In some examples, a device measures finger positions, finger pad sizes,moisture level, acceleration, displacement, and changes in finger padsize for a particular user and compares the measurements to physicalinteraction characteristics measured during subsequent usage of thedevice to verify that a user is an authorized user.

Example Embodiments

such as mobile devices use different mechanisms for authenticating auser. In some instances, authentication may be an application passwordreceived at a software application level. In other examples,authentication may involve an operating system or framework requestingfingerprint scan data, iris scan data, or facial recognition data beforeany operating system or framework functionality can be accessed. Instill other examples, authentication information such as a password isrequested during a boot sequence by a read only memory (ROM). A varietyof levels of authentication are used. Some applications may requirere-authentication after predetermined inactivity periods.Re-authentication typically includes a request for the sameauthentication information received previously.

Biometric mechanisms for authentication are effective but limited. Inmany instances, using biometric authentication alone leads to a numberof false positives or negatives. Consequently, biometric authenticationis often supplemented with passcode mechanisms. Passcode mechanisms aresimilarly effective but limited. Entering passcodes can be cumbersome,particularly on mobile devices because of limited input interfacemechanisms. Some users will simplify mobile device related passcodes toallow ease of entry.

Consequently, techniques and mechanisms are provided to allow forenhanced authentication of a user without negatively impacting userexperience. According to various embodiments, user characteristics suchas device physical interaction characteristics are continually evaluatedto determine whether the current device physical interactioncharacteristics correspond to those of an authorized user. User physicalinteraction characteristics including how the user holds a device whenviewing a screen, how the user holds a device when swiping or typing,how quickly the user taps, types, or swipes, how the user moves thedevice, finger pad area, finger moisture, proximity and number ofsurfaces near the touchscreen during interaction with the device, etc.,can all be used to identify a user with some degree of certainty. Ifuser characteristics information consistently can verify the identity ofthe user with a high degree of certainty, passcode information and/orbiometric information may not be needed. According to variousembodiments, user characteristics information includes user physicalinteraction characteristics information such as tapping and swipingspeed, finger width, device viewing angle, etc. User characteristicsinformation may also include time and location information not includedin the group of user physical interaction characteristics as usedherein.

Time and location information may indicate that a mobile device is usedat the same times every morning and email is accessed every two to threehours during the day. Similarly, it may be determined that a usertypically operates from particular locations at particular times of day.Operating outside of those particular locations or time periods mayindicate that additional authentication is needed. Additionalauthentication may involve only application level authentication, or mayinvolve operating system level authentication and hardware levelauthentication as well. In some instances, the device generates a useridentity confidence score that indicates how likely the user of aparticular device is the owner of the device or an authorized user ofthe device. In some examples the user identity confidence score may beone or more values that indicate the likelihood a current user is anauthorized user.

If the user identity confidence score is low based on available usercharacteristics information, passcode information may be requested morefrequently or additional authentication information on top of passcodesmay be requested. According to various embodiments, if the user identityconfidence score is high based on user characteristics information,passcode information may not be requested for an extended period oftime. In particular embodiments, if the user identity confidence scoreis sufficiently high, passcode information is not requested for anextended period of time even when a device is resuming from standby orsleep mode.

According to various embodiments, the user identity confidence scoreprovides a graduated scale for determining how frequently passcodeinformation or additional authentication information is requested.Requesting passcode information or biometric information less frequentlymay improve user experience while maintaining device security. Inparticular embodiments, if a user identity confidence score is low at aparticular point, additional biometric information or additional usercharacteristics information may be obtained or requested.

FIG. 1 illustrates one particular example of a device that can usemultilevel authentication. According to various embodiments, the device151 may include multiple input interfaces 153 such as touch sensitivedisplay 101, keyboard 103, camera, 105, microphone 107, gyroscope 109,fingerprint scanner 111, global positioning system (GPS) 113, etc. Theinput interfaces may be used to obtain passcode information such aspasswords, pins, and pattern sequences as well as biometric informationsuch as fingerprints, facial pattern scans, and iris scans. According tovarious embodiments, input interfaces may also be used to obtain userphysical interaction characteristics information, such as swipe speedand length, device usage angle, application usage patterns, fingerwidth, etc. In particular embodiments, it is recognized that userphysical interaction characteristics such as tapping speed, swipe speed,finger width, device usage angle, hand temperature, and physicalinteraction characteristics, provide information about who may be usinga particular device. Physical interaction characteristics informationcan be used along with biometric information and passcode information tofurther authenticate a user.

In particular embodiments, the device also includes a passcode store121, a biometric data analyzer component 123, a physical interactioncharacteristics analyzer component 125, a biometric data store 127, anda physical interaction characteristics data store 129. According tovarious embodiments, the passcode store 121, biometric data store 127,and physical interaction characteristics data store 129 maintainpasscodes, biometric data, and physical interaction characteristics datain encrypted form. Newly encrypted data may be compared to previouslyencrypted data maintained on the device. According to variousembodiments, a user identity confidence score generator 131 aggregatesscores from the biometric data analyzer component 123 and the physicalinteraction characteristics analyzer component 125 and identifies whenpasscode information was last obtained. If passcode information wasentered fairly recently and biometric data and physical interaction datais consistent with the identified user, a high identity confidence scoreis maintained. According to various embodiments, even if significanttime has elapsed since passcode information was last entered, as long asbiometric data and physical interaction characteristics data isconsistent with the identified user, passcode information may not berequested for an extended period of time.

In some examples, if a user identity confidence score is sufficientlyhigh, a device may only request some biometric information instead ofrequesting user entry of a passcode. According to various embodiments,the device may also include output interfaces 155 such as speakers 141,display 143, transmitter 145, vibration generator 147, etc. The outputinterfaces can be used to request authentication information from theuser.

Figure illustrates one example of a technique for multi-level passcodeauthentication. At 201, a system ROM requests user authentication. Thesystem ROM may request user authentication during an initial device bootsequence. According to various embodiments, an operating system requestsuser authentication including passcodes at 203. The ROM and/or operatingsystem may verify that authentication sequences correspond with storedauthentication sequences at 205. Otherwise, the user may not be allowedto proceed. User authentication may include passcodes such as passwords,pins, answers to verification questions, code sequences, etc. Theoperating system may also request user biometric information at 207. Thedevice may verify that the biometric information corresponds withmaintained biometric information at 209. At periodic intervals, the ROM,operating system, or even applications may request re-authentication at211. According to various embodiments, the ROM, operating system, andapplications may also request re-authentication after a particulartriggering event at 213. The triggering event may be a device resumingfrom standby or sleep mode.

FIG. 3 illustrates one example of a technique for multi-level passcodeauthentication using a user identity confidence score. According tovarious embodiments, a system or operating system requests passcodeinformation initially at 301. In particular embodiments, a user identityconfidence score is set at 303. According to various embodiments, theuser identity confidence score varies based on the strength of thepassword or errors made in password entry. Biometric information mayalso be obtained or continuously obtained at 305. Biometric informationmay raise or lower the identify confidence score at 307. In someinstances, the user may not be verifiable based on biometricinformation, or biometric information may be very limited and notcontribute much to maintaining a high user identity confidence score.According to various embodiments, user physical interactioncharacteristics are obtained or continuously obtained at 309. Userphysical interaction characteristics may include swipe speed, fingerwidth, angle at which a device is typically held, etc. These physicalinteraction characteristics provide a signature that can help identify aparticular user.

According to various embodiments, the user physical interactioncharacteristics may raise or lower the user identity confidence score at311. According to various embodiments, if the user identity confidencescore drops to a particular threshold, passcode information is requestedor additional authentication information is obtained at 313. Inparticular embodiments, enter passcode information at this point mayinvolve reentry of the same password or pin, responding to a challengequestion, providing additional authentication information, entering adifferent password, etc. If the user identity confidence score remainssufficiently high or sufficient passcode information is entered, the useis provided access to one or more applications on the device. However,if the user identity confidence score is maintained above a confidencethreshold, no additional authentication information may be required. Insome examples, additional authentication information may includeresponses to challenge questions, password information, or pininformation. As time passes after the last passcode entry, the useridentity confidence score may continue to drop even if biometricinformation or physical interaction characteristics information isconsistent with that of a user.

In other examples, a user may elect to set a device to not have to enterany passcode information unless biometric information or user devicephysical interaction characteristics are sufficiently incongruent withthat of the user that a user identity confidence score drops below aconfidence threshold. That is, passcode information and otherauthentication information such as a response to a challenge questionmay be requested only if biometric information and user physicalinteraction characteristics information are insufficient.

FIG. 4 illustrates one example of a technique for obtaining userphysical interaction characteristics. At 401, a device may be calibratedor initialized for the particular user. Capacitive sensors such as thoseon a touchscreen or touchpad detect any capacitance different from thatof air. Capacitive sensors are sensitive to finger positions, finger padsizes, moisture level, acceleration, displacement, changes in finger padsize during motion, etc. Individual users have fingers and fingermotions that are distinctive for that individual, and possibly unique ifmeasured to a sufficiently high level of precision. In particularembodiments, a device measures finger positions, finger pad sizes,moisture level, acceleration, displacement, device angle, changes infinger pad size, etc., during motion while a device is being calibratedfor a particular user at 403.

In particular embodiments, these physical interaction characteristicscan also be measured while the user is entering a passcode or shortlyafter a passcode has been entered at 405. According to variousembodiments, the angle at which a device is held is also measured duringdifferent activities such as swiping, reading, and typing at 407. Inparticular embodiments, non-physical interaction characteristics such astiming and location usage characteristics such as locations of use andtime periods of use are also measured for the particular user at 409.According to various embodiments, physical interaction characteristicsinformation is used to generate a user physical interactioncharacteristics profile at 411. Aspects of the user physical interactioncharacteristics profile can be used to evaluate user actions todetermine a user identity confidence score at 413. In some examples, auser physical interaction characteristics profile is part of a moregeneral user characteristics profile that may include timing andlocation usage characteristics as well as user provided data.

A variety of devices and applications can implement particular examplesof the present invention. FIG. 5 illustrates one example of a computersystem. According to particular example embodiments, a system 500suitable for implementing particular embodiments of the presentinvention includes a processor 501, a memory 503, an interface 511, anda bus 515 (e.g., a PCI bus). When acting under the control ofappropriate software or firmware, the processor 501 is responsible forsuch tasks such as optimization. Various specially configured devicescan also be used in place of a processor 501 or in addition to processor501. The complete implementation can also be done in custom hardware.The interface 511 is typically configured to send and receive datapackets or data segments over a network. Particular examples ofinterfaces the device supports include Ethernet interfaces, frame relayinterfaces, cable interfaces, DSL interfaces, token ring interfaces, andthe like.

In addition, various very high-speed interfaces may be provided such asfast Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces.HSSI interfaces, POS interfaces, FDDI interfaces and the like.Generally, these interfaces may include ports appropriate forcommunication with the appropriate media. In some cases, they may alsoinclude an independent processor and, in some instances, volatile RAM.The independent processors may control such communications intensivetasks as packet switching, media control and management.

According to particular example embodiments, the system 500 uses memory503 to store data and program instructions and maintain a local sidecache. The program instructions may control the operation of anoperating system and/or one or more applications, for example. Thememory or memories may also be configured to store received metadata andbatch requested metadata.

Because such information and program instructions may be employed toimplement the systems/methods described herein, the present inventionrelates to tangible, machine readable media that include programinstructions, state information, etc. for performing various operationsdescribed herein. Examples of machine-readable media include hard disks,floppy disks, magnetic tape, optical media such as CD-ROM disks andDVDs; magneto-optical media such as optical disks, and hardware devicesthat are specially configured to store and perform program instructions,such as read-only memory devices (ROM) and programmable read-only memorydevices (PROMs). Examples of program instructions include both machinecode, such as produced by a compiler, and files containing higher levelcode that may be executed by the computer using an interpreter.

Although many of the components and processes are described above in thesingular for convenience, it will be appreciated by one of skill in theart that multiple components and repeated processes can also be used topractice the techniques of the present invention.

While the invention has been particularly shown and described withreference to specific embodiments thereof it will be understood by thoseskilled in the art that changes in the form and details of the disclosedembodiments may be made without departing from the spirit or scope ofthe invention. It is therefore intended that the invention beinterpreted to include all variations and equivalents that fall withinthe true spirit and scope of the present invention.

What is claimed is:
 1. A method for user authentication on a mobiledevice, the method comprising: obtaining physical interactioncharacteristics information for a user of a device; generating a userphysical interaction characteristics profile; and recurrently comparingcontinually measured physical interaction characteristics informationwith the user physical interactions characteristics profile in order toconsistently authenticate the user without the need for passcodeinformation or additional authentication information, wherein aconfidence score provides a graduated scale for determining howfrequently passcode information or additional authentication informationis requested.
 2. The method of claim 1, wherein physical interactioncharacteristics information is compared with the user physicalinteraction characteristics profile to generate the confidence score. 3.The method of claim 1, wherein physical interaction characteristicsinformation is obtained during or shortly after the user enters passcodeinformation.
 4. The method of claim 3, wherein physical interactioncharacteristics information comprises tapping and swiping speed andacceleration.
 5. The method of claim 3, wherein physical interactioncharacteristics information comprises finger pad area.
 6. The method ofclaim 3, wherein physical interaction characteristics informationcomprises device angle.
 7. The method of claim 4, wherein physicalinteraction characteristics information comprises device angle measuredduring swiping, reading, and typing.
 8. The method of claim 7, whereinnon-physical interaction characteristics including location and timeinformation are evaluated to generate the confidence score.
 9. Themethod of claim 8, wherein additional authentication informationcomprises passcode information and biometric data.
 10. The method ofclaim 1, wherein a sufficiently high confidence score authorizes theuser to access an application on the device.
 11. A system for userauthentication on a mobile device, the system comprising: a plurality ofinput interfaces configured to obtain physical interactioncharacteristics information for a user of a device; a physicalinteraction characteristics analyzer configured to generate a userphysical interaction characteristics profile; and a user identityconfidence score generator configured to recurrently compare continuallymeasured physical interaction characteristics information with the userphysical interactions characteristics profile in order to consistentlyauthenticate the user without the need for passcode information oradditional authentication information, wherein a confidence scoreprovides a graduated scale for determining how frequently passcodeinformation or additional authentication information is requested. 12.The method of claim 11, wherein physical interaction characteristicsinformation is compared with the user physical interactioncharacteristics profile to generate the confidence score.
 13. The systemof claim 11, wherein physical interaction characteristics information isobtained during or shortly after the user enters passcode information.14. The system of claim 13, wherein physical interaction characteristicsinformation comprises tapping and swiping speed and acceleration. 15.The system of claim 13, wherein physical interaction characteristicsinformation comprises finger pad area.
 16. The system of claim 13,wherein physical interaction characteristics information comprisesdevice angle.
 17. The system of claim 14, wherein physical interactioncharacteristics information comprises device angle measured duringswiping, reading, and typing.
 18. The system of claim 17, whereinnon-physical interaction characteristics including location and timeinformation are evaluated to generate the confidence score.
 19. Thesystem of claim 18, wherein additional authentication informationcomprises passcode information and biometric data.
 20. A non-transitorycomputer readable storage medium comprising computer code for performinguser authentication on a mobile device, the computer code comprisinginstructions for: obtaining physical interaction characteristicsinformation for a user of a device; generating a user physicalinteraction characteristics profile; and recurrently comparingcontinually measured physical interaction characteristics informationwith the user physical interactions characteristics profile in order toconsistently authenticate the user without the need for passcodeinformation or additional authentication information, wherein aconfidence score provides a graduated scale for determining howfrequently passcode information or additional authentication informationis requested.